feat(notification): add provider-agnostic email adapter with templates &n mock provider#152
Merged
ahmadogo merged 1 commit intoMentoNest:mainfrom Jan 29, 2026
Conversation
…s and mock provider
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✉️ Email Notification Adapter
This PR introduces a provider-agnostic email notification system with support for pluggable providers, templated emails, and a mock provider for development and testing.
🎯 Purpose
Improve notification reliability and flexibility by decoupling email delivery from specific providers while enabling reusable, event-based email templates.
✅ What’s Included
🔌 Provider-Agnostic Email Adapter
EmailAdapterinterface🧪 Mock Email Provider
📨 Templated Emails
⚙️ Configuration
📊 Logging
email.logger.ts)🧪 Tests
🧩 Example Usage